Pin definitions when building an older version #4155
Merged
+39
−23
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a follow-up to #4007, in which I had neglected to pin definitions for key terms to the published recommendation when building for 2.1.
termsMap
definition to the Eleventy config (where all other target-version-dependent assignments are made), to be passed into theCustomLiquid
constructortermsMap
references withinCustomLiquid
to use an instance variable set in the constructorloadRemoteGuidelines
to account for pre-processed terms contentrender
processing for pages not being output for 2.1 (to avoid irrelevant error messages as well as save time)